home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
QRZ! Ham Radio 1
/
QRZ Ham Radio Callsign Database - December 1993.iso
/
arrl
/
emergenc.ybs
< prev
next >
Wrap
Text File
|
1993-11-21
|
10KB
|
217 lines
EMERGENCY BBS FOR TACTICAL EOC-EOC PACKET TRAFFIC
Tactical traffic between Emergency Operations Centers (EOCs) often
consists of short messages requesting or providing status updates. As
is usual, the use of packet radio can provide a modicum of security for
such messages while also freeing up voice channels for other uses. For
the purposes of this document, "EOC" should be regarded in the broad
sense to signify major emergency operations locations, such as city
EOCs, County Communications, Red Cross chapter headquarters, etc. This
document describes a packet radio scheme for handling EOC-EOC tactical
traffic in a widespread emergency that was discussed during the Santa
Clara County EC Council meeting on March 1, 1990.
Although there are many ways in which packet radio could handle such
message traffic (e.g., TCP/IP, BBS, keyboard to keyboard), the majority
of hams who have used packet radio are already well-versed in BBS usage.
In order to have an easily accessible system that requires minimal
training, can be used on a variety of computers, and tolerates many
different packet stations, it appears easiest to rely on a system that
uses BBS technology and terminology. A further advantage of a BBS is
its ability to automatically store the traffic that was passed; killed
messages do not actually disappear until a sysop command is given and
can remain as a log of the event.
The following assumption is made within Santa Clara County: each EOC
will have a packet operator who knows how to connect to a BBS using
AX.25 protocol. The EOC or operator may have more capabilities and
training (computer, knowledge of TCP/IP, etc.), but in an emergency, it
makes the most sense to configure a system that requires only minimal
skill and equipment. The simpler the system is, the more likely it is
that it will be functional in an area-wide disaster.
One method of passing traffic between EOCs might be to ask each EOC to
connect directly to each of the other EOCs. This type of multi-
connected, keyboard to keyboard network is impractical to use in an
emergency as a good path must be established between all pairs of
locations. A much more realistic network is a star-shaped topology with
a central BBS at a moderately high location to which all of the EOCs
connect to send and receive traffic. In this configuration, each EOC
need only provide a good path to the central BBS.
It is essential for the central emergency-oriented BBS to be separate
from the normal BBS network. In a disaster, the stations using the
emergency BBS must not be distracted by such things as "for sale"
messages, general QSTs, and health and welfare traffic; these services
are already handled well by the standard BBS network.
A further requirement for the central emergency-oriented BBS is that it
have multiple connect capabilities. Many EOCs need to pass traffic and
must be able to connect at the same time rather than wait for the BBS to
be free. The exact maximium number of active stations on one frequency
is limited by the 1200 baud data rate of many current TNCs which implies
about 4-6 stations on the same frequency. In order to handle 10 or more
EOCs, multiple ports are also required.
A final requirement for the central emergency BBS is automatic emergency
power as power failure is likely during a widespread event.
In the event that the coverage area is extensive or the number of EOCs
is large enough to overload one computer, two or more emergency BBSes
can be established which are linked by a backbone frequency in a small
network. This scheme also provides back up capabilities in case one of
the BBSes malfunctions. For example, in Santa Clara County, it may be
useful to establish a northern BBS and a southern BBS and to connect the
two in a backbone.
Our emergency BBS system is currently composed of the following
elements:
1. A multi-connect BBS at a central high level location in the county
on emergency power. We have selected at this time the "BB" mailbox
program by AA4RE because it provides many connections on each of
several ports.
2. Packet stations at the various EOCs (including County Comm and other
major locations such as Red Cross Chapters).
During the emergency, the EOC stations all connect to the BBS as
required. The EOC stations can send messages to other EOCs, receive
messages addressed to them, and then disconnect until they again need to
send or receive traffic. We have defined a particular convention for
setting callsigns and beacon text which makes traffic passing very
convenient. The convention we use for sending and receiving messages is
described at the end of this document. In essence, the stations set the
AX.25 callsign (i.e., MYCALL) to the tactical ID, and the amateur
station callsign is placed in the beacon text with a 10 minute beacon
interval. It is expected that in the near future the BB software will
be enhanced to implement tactical ID's in a more elegant manner; in this
sense, the scheme described here is only a temporary stopgap measure.
In the case that an EOC has a personal mailbox running in their TNC, the
central BBS can be configured to automatically forward mail to this TNC.
This means that the EOC need only connect to the central BBS when
sending traffic; it is not necessary to connect to see if there is any
pending traffic to be received.
To test these concepts and to have a system on the air immediately in
case the next earthquake occurs tomorrow, we have set up such an
emergency BBS system for testing and immediate use if a disaster occurs.
This system uses donated personal equipment and a site provided by the
IBM Amateur Radio Club. The current BBS system configuration is:
BBS callsign = WN6I-6
Frequency = 223.56 (in the near future, a 2m port will be added)
BBS program = BB 2.8
Location = IBM Almaden Research Center in San Jose at 1000 feet,
with automatic emergency power and automatic restart
We encourage EOC packet operators to connect to this BBS to determine if
a good path exists. This will help us to determine if a second BBS is
required and where it should be located. If required, you may choose to
use one of the digipeaters on 223.56 such as NT6V-4 and N6IIU-4,
although it would be best to locate the emergency BBS(s) where no
digipeating is required.
This system will evolve with time as we gain experience; however, it is
most important to have at least a starting system on the air. As usual,
comments and suggestions are welcome.
WN6I/N6KL/N6MWD 3/10/90
========================================================================
EMERGENCY BBS OPERATION RULES
BY: WN6I, N6KL, N6MWD
The following information provides the abbreviations to be used when
sending messages from EOC to EOC via the BB Emergency BBS.
1. Each station has a short-tactical ID as shown in the list below.
Set MYCALL to your tactical ID. For example, San Jose EOC would set
MYCALL to SJEOC.
2. At the same time, to satisfy FCC regulations for station
identification, the beacon should be set to a 10 minute interval,
and put your amateur radio callsign in the message text. For
example:
BEACON every 60
BTEXT San Jose EOC station, callsign AA6HX
NOTE: After the event is over, be sure to remember to restore MYCALL
to your FCC-issued callsign AND be sure to type "BEACON EVERY 0" to
turn off beacon generation!!
3. Even though the emergency BBS allows many stations to be connected
at the same time, stay connected only as long as necessary to get
your mail and/or to send mail.
4. With these assumptions, you can send mail from one EOC to another by
simply using the tactical callsign. For example:
s lgeoc (to send a message to los gatos)
5. For the title of the message, use something descriptive about the
person to whom the message is addressed. For example:
Msg for Mr. Joe Smith
6. As always, within the message, use good amateur practice by
specifying:
To: Name and Position
From: Name and Position
Text
(Date and time are automatic.)
7. If you are SJEOC, see what messages have been sent to you by typing:
l> sjeoc
This will allow you to see what messages are "to" San Jose. Then
read the message by typing:
r # (# is the actual message number)
Or, use the command "rm", which means "read mine".
8. To see if a message you sent has been read, look at the message
status field. A "y" means the messge has been read by the
recipient. You can delete messages sent to you or sent by you as
required using "k #".
9. Here are the standard abbreviations to use:
CAMEOC Campbell
CUPEOC Cupertino
GILEOC Gilroy
LAEOC Los Altos
LAHEOC Los Altos Hills
LGEOC Los Gatos
MILEOC Milpitas
MHEOC Morgan Hill
MTVEOC Mountain View
PAEOC Palo Alto
SJEOC San Jose
SCEOC Santa Clara
SAEOC Saratoga
STAEOC Stanford
SUNEOC Sunnyvale
CNTYCOM County EOC (at County Comm)
PGE Pacific Gas & Electric
SJRC San Jose Red Cross
PARC Palo Alto Red Cross
LGRC Los Gatos Red Cross
This message will be updated to add new abbbreviations as necessary.
Further information is available by contacting Weo Moerner, WN6I @ K3MC
BBS in San Jose, California.